Skip to main content

Chapter 2 - Infrastructure as Code

The origins of IaC and why we use it.

Traditional​

  • 5-6 days between environments, giving us 30 days from start to finish
  • Drift between environments
  • no CI on the environments - you get 1 dev and not multiple dev.
  • delay in one environment pushes delays across later environments

IaC​

  • Check in your code into the repo
  • CI/CD pipeline then runs to build the infrastructure
  • Creating all of the environments at once

Visibility​

  • Don't need to check the Portal for the infrastructure

Stability​

  • you change one thing in the console, you can break things
  • approvals to change to infrastructure via source control.

Scalability​

  • write once, use many times

###Security

  • Using published, known modules and known providers.

Audit​

  • records what is done in the state files and by who in the source control.